-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multistream specs #15603
base: develop
Are you sure you want to change the base?
Multistream specs #15603
Conversation
AER Report: CI Core ran successfully ✅AER Report: Operator UI CI ran successfully ✅ |
f373e71
to
358a742
Compare
00ca59b
to
13192ab
Compare
} | ||
} | ||
|
||
func (s *streamRegistry) Get(streamID StreamID) (strm Stream, exists bool) { | ||
func (s *streamRegistry) Get(streamID StreamID) (p Pipeline, exists bool) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the relation between job ids, stream ids, and pipeline ids? Seems like job and stream are analogous, and then 1 pipeline can have many streams (which is a specific type of job). Is that correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this is a bit confusing. A job
has exactly one pipeline_spec
and those have two different IDs (we almost exclusively use the jobID
to reference it though). stream_id
is a completely different thing. So a job has one pipeline which may contain many stream IDs.
// This is a hack to support the legacy "Quote" case. | ||
// Future stream specs should use streamID tags instead. | ||
switch len(finaltrrs) { | ||
case 1: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where do these case values come from? Why is case 2 skipped?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I see it's the number of results in the task run..Won't flexible schema result in a variable number of results - how would you know if it's benchmark/bid/ask vs bid/ask/marketDepth for example? Or is a taskRunResult just one stream result, and one stream result always one datapoint?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is only needed for when you specify streamID at the job level, which this PR takes us away from. So we need to continue supporting this for the old use-case but for new cases its not relevant since the task can be tagged with a streamID
446fb9c
to
f582bce
Compare
dcea97e
to
8b66587
Compare
Quality Gate passedIssues Measures |
Requires
Supports